| global.devLicense | string | The developer license provided by customer support for using Eggplant DAI. | nil |
| global.execLicense | string | The execution license provided by customer support for using Eggplant DAI. | nil |
| global.ingress.className | string | Which ingress-nginx class to use for the ingress. | "nginx" |
| global.ingress.host | string | Hostname for DAI ingress. | "dai.example.com" |
| global.keycloak.host | string | | "kc-dai.example.com" |
| global.keycloak.password | string | Password for the Keycloak admin user. with a secret. | "admin" |
| global.keycloak.user | string | Username for the Keycloak admin user. | "admin" |
| global.objectStorage.aws | object | Configures the AWS provider. | {"awsAccessKeyId":"eggplant","awsAccessKeyIdKey":"","awsSecretAccessKey":"eggplant","awsSecretAccessKeyKey":"","existingSecret":"","region":"eu-west-1"} |
| global.objectStorage.aws.existingSecret | string | Existing secret overrides the value of awsAccessKeyId and awsSecretAccessKey. | "" |
| global.objectStorage.bucketName | string | Name of the object storage bucket. | "eggplant" |
| global.objectStorage.minio | object | Configures the Minio provider. if rootUser and rootPassword are set, you can use the included minio chart by setting minio.enabled to true without further configuration. if you want to use an existingSecret, you'll need to set the secret name in minio.auth.existingSecret. The secret will need to have the keys root-user and root-password. | {"endpoint":"","existingSecret":"","rootPassword":"eggplant","rootPasswordKey":"","rootUser":"eggplant","rootUserKey":""} |
| global.objectStorage.minio.endpoint | string | Endpoint of the minio instance. Only set this if you're not using the included minio chart. | "" |
| global.objectStorage.provider | string | Which object storage provider is used. Valid values are 'minio' or 'aws'. | "minio" |
| global.postgresql.auth.postgresPassword | string | Password for the postgres admin user. Used by DAI for authentication with the PostgreSQL instance and inherited by the postgresql sub-chart to configure the postgres user. | "postgres" |
| global.postgresql.host | string | Hostname of the PostgreSQL instance to be used by DAI. | "postgres" |
| global.postgresql.ttdbName | string | Name of the main database used by DAI. | "ttdb" |
| global.postgresql.username | string | Custom user to create. Used by DAI for authentication with the PostgreSQL instance and inherited by the postgresql sub-chart to configure the PostgreSQL deployment. | "postgres" |
| global.rabbitmq.erlangCookie | string | The RabbitMQ Erlang cookie. It will either be set from the value of rabbitmq-erlang-cookie in the secret dai-rabbitmq or it will be set to a random string. | nil |
| global.rabbitmq.existingSecret | string | An existing secret with rabbitmq-password and rabbitmq-erlang-cookie keys in it. Overrides rabbitmq.password and rabbitmq.erlangCookie. | "" |
| global.rabbitmq.host | string | Hostname of the RabbitMQ instance. | "rabbitmq" |
| global.rabbitmq.password | string | Password for DAI to authenticate with RabbitMQ. If this is not set, it will either be set to the value of rabbitmq-password in the secret dai-rabbitmq or it will be set to a random string. | nil |
| global.rabbitmq.port | int | The port the RabbitMQ instance is running on. | 5672 |
| global.rabbitmq.username | string | Username for DAI to authenticate with RabbitMQ as. | "rabbitmq" |
| keycloak | object | Configuration for the Bitnami Keycloak sub-chart. | {"auth":{"adminPassword":"admin","adminUser":"admin"},"enabled":true,"externalDatabase":{"database":"keycloak","existingSecret":"","host":"postgres","password":"fake","user":"postgres"},"fullnameOverride":"keycloak","httpRelativePath":"/auth/","ingress":{"enabled":false},"initContainers":[{"command":["sh","-c","until pg_isready -U ${KEYCLOAK_DATABASE_USER} -h ${KEYCLOAK_DATABASE_HOST} -p ${KEYCLOAK_DATABASE_PORT}; do echo \"waiting for PostgreSQL\"; sleep 5; done"],"envFrom":[{"configMapRef":{"name":"keycloak-env-vars"}}],"image":"docker.io/bitnami/postgresql:14.5.0-debian-11-r35","imagePullPolicy":"IfNotPresent","name":"wait-for-postgresql"}],"postgresql":{"enabled":false}} |
| keycloak-realm-provisioner.smtp.auth | string | | "" |
| keycloak-realm-provisioner.smtp.enabled | string | Whether to configure SMTP in Keycloak for sending emails. | "no" |
| keycloak-realm-provisioner.smtp.existingSecret | string | | "" |
| keycloak-realm-provisioner.smtp.from | string | | "" |
| keycloak-realm-provisioner.smtp.host | string | | "" |
| keycloak-realm-provisioner.smtp.password | string | | "" |
| keycloak-realm-provisioner.smtp.port | string | | "" |
| keycloak-realm-provisioner.smtp.ssl | string | | "" |
| keycloak-realm-provisioner.smtp.tls | string | | "" |
| keycloak-realm-provisioner.smtp.user | string | | "" |
| keycloak-user-provisioner.adminUsers | object | This mapping lists the DAI admin users to create. You can specify multiple admin users, each in a separate key, e.g. adminUsers.myAdmin, adminUsers.anotherAdmin. Each specified admin user must have all the fields shown under adminUsers.daiAdmin. | {"daiAdmin":{"email":null,"firstName":null,"lastName":null,"password":null,"username":null}} |
| keycloak-user-provisioner.adminUsers.daiAdmin.password | string | must be >= 12 characters long. | nil |
| keycloak.auth | object | Configuration for the initial admin user. | {"adminPassword":"admin","adminUser":"admin"} |
| keycloak.enabled | bool | Must be set to true - we do not support using your own Keycloak. | true |
| keycloak.externalDatabase | object | Configure the database to be used by Keycloak for persistence. If using the bundled PostgreSQL instance and changing any parameters, this needs to be updated to match. | {"database":"keycloak","existingSecret":"","host":"postgres","password":"fake","user":"postgres"} |
| keycloak.fullnameOverride | string | Changing this will impact the name of the service created by the Bitnami chart. If you change this, DAI may not behave as expected. | "keycloak" |
| keycloak.httpRelativePath | string | The path to publish Keycloak resources at. this is needed for compatibility with old Keycloak versions. DAI depends on this and it must not be changed. | "/auth/" |
| keycloak.ingress.enabled | bool | If the ingress config deployed by the Bitnami keycloak chart is deployed or not. This must be false as we are shipping our own ingress. | false |
| keycloak.initContainers | list | Adds an init container to prevent Keycloak from coming up before PostgreSQL is ready. | [{"command":["sh","-c","until pg_isready -U ${KEYCLOAK_DATABASE_USER} -h ${KEYCLOAK_DATABASE_HOST} -p ${KEYCLOAK_DATABASE_PORT}; do echo \"waiting for PostgreSQL\"; sleep 5; done"],"envFrom":[{"configMapRef":{"name":"keycloak-env-vars"}}],"image":"docker.io/bitnami/postgresql:14.5.0-debian-11-r35","imagePullPolicy":"IfNotPresent","name":"wait-for-postgresql"}] |
| keycloak.postgresql | object | If the Keycloak chart configures its own PostgreSQL instance. We re-use the same postgres instance as the rest of DAI, so leave this false. | {"enabled":false} |
| minio | object | Configuration for the Bitnami Minio sub-chart. | {"auth":{"existingSecret":"dai-objectstorage"},"clientImage":{"tag":"2022.2.2-debian-10-r3"},"enabled":true,"fullnameOverride":"minio","image":{"tag":"2022.2.5-debian-10-r0"},"persistence":{"enabled":true}} |
| minio.auth.existingSecret | string | This secret is automatically populated by the values in global.objectStorage.minio.rootUser and rootPassword. If you provide an existing secret in global.objectStorage.minio, you must update this to match. The secret must have keys root-user and root-password. | "dai-objectstorage" |
| minio.enabled | bool | Set this to false if you want to use your own object storage service, e.g. AWS S3. | true |
| minio.fullnameOverride | string | Impacts the service name created by the Bitnami chart. If this changes, it could break DAI. | "minio" |
| minio.persistence.enabled | bool | Persist stored objects to a PVC. Disabling this may result in lost data. | true |
| postgresql | object | Configuration for the Bitnami postgresql sub-chart. | {"enabled":true,"fullnameOverride":"postgres","primary":{"extraEnvVars":[{"name":"POSTGRESQL_DATABASE","value":"keycloak"}],"persistence":{"enabled":true}}} |
| postgresql.enabled | bool | Set to false if using an alternative PostgreSQL installation. | true |
| postgresql.fullnameOverride | string | Impacts the name of the service created. If this is changed, will most likely need to update global.postgresq.host to work. | "postgres" |
| postgresql.primary.extraEnvVars[0] | object | POSTGRESQL_DATABASE environment variable is the name of a database to create on the PostgreSQL instance at initial deployment. The 'keycloak' database must exist for DAI to work, however you choose to create it. | {"name":"POSTGRESQL_DATABASE","value":"keycloak"} |
| postgresql.primary.persistence.enabled | bool | Controls whether PostgreSQL data is persisted in a PVC. Setting this to false could result in data loss. | true |
| rabbitmq | object | Configuration for the Bitnami RabbitMQ chart. | {"auth":{"existingErlangSecret":"dai-rabbitmq","existingPasswordSecret":"dai-rabbitmq","username":"rabbitmq"},"enabled":true,"fullnameOverride":"rabbitmq","persistence":{"enabled":true}} |
| rabbitmq.auth.existingErlangSecret | string | Secret to fetch the RabbitMQ Erlang cookie from. Must have rabbitmq-erlang-cookie. DAI assumes this and existingPasswordSecret are the same. If these change, must update global.rabbitmq.existingSecret. | "dai-rabbitmq" |
| rabbitmq.auth.existingPasswordSecret | string | Secret to fetch the RabbitMQ user password from. Must have rabbitmq-password key in it. If this changes, must update global.rabbitmq.existingSecret. | "dai-rabbitmq" |
| rabbitmq.auth.username | string | Default RabbitMQ user to create. If this changes, must update global.rabbitmq.username to match. | "rabbitmq" |
| rabbitmq.fullnameOverride | string | Changing this could impact the service name created by the Bitnami chart and break DAI. | "rabbitmq" |